valiance-clan: 82f5ff2257929a055a1a3352020a53c0ba07ee38..7f1ac53a6b2f1bb132188d3637acc93a6a3946e3

This plugin requires a review from a Plugin Hub maintainer. The reviewer will request any additional changes if needed.

Internal use only: Reviewer details Maintainer details

• your build in runelite-plugin.properties should be standard
• use of client.menuAction is not allowed

• your build in runelite-plugin.properties should be standard

Will make this change

* use of client.menuAction is not allowed

This must be a new ruling. I'll look what other plugins are doing for taking Collection Log data now.

Edit: Looks like temple is still using client.menuAction. Any suggestions of plugins with new behavior for this?

• use of client.menuAction is not allowed

this may actually be ok, although if there is a way to accomplish whatever you're doing without menuAction please let me know

• use of client.menuAction is not allowed

this may actually be ok, although if there is a way to accomplish whatever you're doing without menuAction please let me know

When opening the collection log, only the items which are on the current visible menu are able to be grabbed. Clicking the search button loads the data for all items regardless of page. So, what we are doing here is creating a fake search button click when the Collection Log opens, in order to load all of the item data.

Temple's plugin has a button you click on to sync it where as this plugin does it once the Collection log loads, without user input. We can add a button to map it to if that feels more correct. Otherwise, we'll just be asking our users to click the search button which is a little jank but we can live with.

Accidentally rebased off an old master causing the above issue. Didn't need to rebase at all. Ooops